Hi @karthikeayan ; thanks for offering this up.

There are two different changes rolled up here together. I like them both, but we need to separate them out into separate PRs for management. What I see here is:

• support for an image based on debian-stretch-slim, that installs an actual mysql (not mariadb) client, to avoid current (and potential future) compatibility issues.
• Description and sample files for deploying into kubernetes

Let's do the following:

1. Create one PR just for the Kubernetes work. Roll that documentation into the main README.md, or at least have it as a separate file with a link to it. Those don't go under debian-mysql-core/ but in the main dir
2. Reuse this PR (or create a clean new one) that just builds the image as an option based on debian so the installed client is true mysql.

For the latter, I am going to consider creating a separate mariadb-backup for the current implementation, and have this be mysql-backup for true mysql. I need to think through how to avoid duplicate work, but it should be doable. Let's get the PR in first.

Hi @karthikeayan . I changed CI to run on GitHub actions. Do you mind rebasing it?

@deitch did rebase

I am not quite sure what to make of this. It looks like a whole separate dir named debian-mysql-core/, but what is in it and how is it used?